-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NO-ISSUE: Use the SonataFlow icon in the nav bar #694
Conversation
🎊 PR Preview ea1866d has been successfully built and deployed. See the documentation preview: https://sonataflow-docs-preview-pr-694.surge.sh |
@@ -1,3 +1,3 @@ | |||
.navbar { | |||
background: #085870 !important; | |||
background: #0476d0 !important; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wmedvede can you try one of these colors and see which one matches better?
Deep Navy Blue (#002F5F) – A dark blue that matches the logo's darker tones, providing a professional and elegant look.
Teal Blue (#007E99) – A slightly lighter shade of blue to complement the lighter parts of the logo and create a fresh, modern vibe.
Charcoal Black (#1C1C1C) – A neutral and bold black that can make the logo stand out while maintaining simplicity.
Soft Orange (#F4A261) – A muted orange that aligns with the logo’s orange wave, creating a warm and inviting feel.
Cool Gray (#E0E0E0) – A neutral light gray that contrasts the logo without overshadowing it, ideal for a clean design.
AI suggested it based on our colors.
Pretty cool, @wmedvede!! I liked the option four the most. wdyt? |
great! thanks for voting. |
I have incorporated the white circled icon kindly provided by @Masha. Examples here: |
Description:
Please make sure that your PR meets the following requirements:
Issue-XYZ Subject
[0.9.x] Issue-XYZ Subject
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.